WIP.

This ambitious refactor aims to decouple the CLI from the core logic of npkill, exposing the core through a simple and clean interface that can be imported and reused in other projects.

How does this affect regular users?

It doesn't. Npkill will continue to work as expected (except for a few internal improvements under the hood).

The situation before

Previously, there was no separation. Npkill was a monolith: both the search engine and the TUI were tightly coupled as a single unit.

The situation now

Internally, the project has been split into two packages: core and cli.

• The core logic is now fully isolated from the TUI layer and exposed through a basic yet robust API.
• This enables npkill to be imported into other applications, allowing for custom implementations, such as automated cleanup scripts or tightly controlled periodic tasks.
• The API is based on RxJS, just like the core itself, allowing real-time control.

The CLI package remains private and internal to npkill, since there's no practical reason to reuse that part outside the main project.

Why?

• More modular and maintainable code.
• Greater extensibility and experimentation.
• And more important, allow to create other things based on this package, like npkill web (in progress).

This API (and a lot of other features) will be released together with the arrival of v1.0.